home *** CD-ROM | disk | FTP | other *** search
- Path: news.ess.harris.com!usenet
- From: "Scott J. Cloutier" <sjc@rfc.comm.harris.com>
- Newsgroups: comp.sys.m68k
- Subject: Re: MC68360 In circuit emulators
- Date: 15 Jan 1996 17:40:01 GMT
- Organization: Harris Corporation - RF Communications
- Message-ID: <4de3hh$r19@su102w.ess.harris.com>
- References: <4chik9$n2n@su102w.ess.harris.com> <4cqnh1$7u5@luggage.rednet.co.uk> <4d13jp$oet@su102w.ess.harris.com> <4d2tpj$otb@luggage.rednet.co.uk>
- NNTP-Posting-Host: adm01.rfc.comm.harris.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
-
- >If you are using Microtec's C++ compiler, you are producing IEEE695
- >format images which can be converted into EST symbol format, using
- >their supporting tools, for use with the trace capability in the
- >emulator. This gives complete, non-intrusive, source and assembly
- >level trace and breakpoints.
- >Have you tried this?
- >
- >Is there any reason why this does not work, or does not give you the
- >functionality you require?
-
- Actually, most of the tools vendors seem to add on proprietary
- informationonto the IEEE695 format. We are using SDS right now,
- and I found out that the EST emulator ignores thier custom extensions.
-
- (I think...)
-
- - Scott
-
-